8 MyID Client Service error codes
This section contains the list of errors produced by the MyID Client Service that may occur when using the MyID Operator Client.
To assist with the diagnosis of issues, Intercede support may guide you to enable logging for the client service; you can then provide these logs to customer support for analysis. For information on configuring logging, see the MyID Client Service section in the Configuring Logging guide.
Error Code |
881030 |
Text |
An unknown error has occurred |
Details |
The MyID Client Service encountered an unknown error from which it could not recover. |
Solution |
There may be more information about the error in the client log, if logging is enabled. |
Error Code |
3102130 |
Text |
Provided image path does not exist or is inaccessible. |
Details |
The MyID Image Editor uses the current user's temporary folder as a cache, but it is unable to access it. |
Solution |
Ensure the user's temporary folder has appropriate permissions. By default, this can be found at %userprofile%\AppData\Local\Temp |
Error Code |
3102131 |
Text |
Failed to load image. This is usually because it is in an unsupported format. |
Details |
The MyID Image Editor was unable to process the provided data as a supported image type. |
Solution |
Ensure the provided image is in one of the supported formats:
|
Error Code |
10000224 |
Text |
Configuration File Error: Invalid configuration |
Details |
The MyIdClientService.dll.config file is invalid, but the MyID Client Service could not determine the problem. |
Solution |
Ensure the configuration file exists, is populated with valid XML, and does not contain any duplicate or invalid values. |
Error Code |
10000225 |
Text |
Configuration File Error: Server setting not found. Make sure you have provided a valid server or SSA install path. |
Details |
No Server has been specified, and there is no path to a Self-Service App installation with a Server value in its configuration file. |
Solution |
Ensure the Server node in the configuration file has a valid value, or, if you are using the Self-Service App's configuration, ensure that Self-Service App's Server configuration contains a valid value and the MyID Client Service's SsaPath node contains the correct path to the Self-Service App program file. |
Error Code |
10000226 |
Text |
Configuration File Error: DataSource setting not found. Make sure you have provided a valid DataSource or SSA install path. |
Details |
No DataSource URI has been specified, and there is no path to an Self-Service App installation with a DataSource value in its configuration file. |
Solution |
Ensure the DataSource node in the configuration file has a valid value, or, if you are using the Self-Service App's configuration, ensure that Self-Service App's DataSource configuration contains a valid value and the MyID Client Service's SsaPath node contains the correct path to the Self-Service App program file. |
Error Code |
10000229 |
Text |
A MyID Client Service window is already open. Please close any MyID Client Service windows and try again. |
Details |
The MyID Client Service can display only a single applet window at a time, but an operation was attempted that requires a window to be displayed while one was already open. |
Solution |
Close any open MyID Client Service windows and try again. |
Error Code |
10000233 |
Text |
Failed to initialise translations - see the log for more details. |
Details |
There was an error updating the local translation cache. |
Solution |
There may be more information about the error in the client log, if logging is enabled. |
Error Code |
10000234 |
Text |
Configuration File Error: Invalid DisableAccessControl setting provided; value must be either 'true' or 'false'. |
Details |
An invalid value has been provided for the DisableAccessControl configuration. |
Solution |
Ensure the DisableAccessControl configuration has a value of either true or false. Removing the node from the configuration file is the equivalent of it having a value of false. |
Error Code |
10000235 |
Text |
Configuration File Error: Invalid AccessControlAllowOrigin setting provided; value must contain at-least one fully-resolved URI, or, in the case of multiple allowed-origins, a comma-separated list of fully-resolved URIs. |
Details |
Either the AccessControlAllowOrigin configuration has not been specified (and DisableAccessControl is not set to true), an invalid value has been supplied, or the value is not in the expected format. |
Solution |
Ensure the AccessControlAllowOrigin configuration is valid; value must contain at-least one fully-resolved URI, or, in the case of multiple allowed-origins, a comma-separated list of fully-resolved URIs. |
Error Code |
10000228 |
Text |
Failed to bind to local web-socket port. Make sure another application is not running and consuming your port. |
Details |
The MyID Client Service was unable to establish a binding to the port configured in the WebSocketPort configuration (default of 8081). |
Solution |
Close any applications that are consuming the port that the MyID Client Service is trying to bind to. If this is not possible, you can change the port the MyID Client Service uses by updating its WebSocketPort configuration; note that you must make the equivalent configuration change on the Operator Client server or it will not know which port to use to connect to the MyID Client Service . |
Error Code |
10000230 |
Text |
An error occurred when communicating with EdeficeSmartCard. |
Details |
An unknown error occurred communicating with an internal component (EdeficeSmartCard). |
Solution |
There may be more information about the error in the client log, if logging is enabled. |
Error Code |
10000231 |
Text |
An error occurred when communicating with Enveloper. |
Details |
An unknown error occurred communicating with an internal component (Enveloper). |
Solution |
There may be more information about the error in the client log, if logging is enabled. |
Error Code |
10000232 |
Text |
An error occurred when communicating with SoftwareCrypto. |
Details |
An unknown error occurred communicating with an internal component (SoftwareCrypto). |
Solution |
There may be more information about the error in the client log, if logging is enabled. |
8.1 .NET Networking errors
Networking errors from .NET are presented directly; these are not produced by the MyID Client Service, and so do not have Intercede error codes.
These errors are presented with the following text:
MyID Client Service encountered a communication error.
For example:
For more information, see the Microsoft documentation:
docs.microsoft.com/en-us/dotnet/api/system.net.sockets.socketerror